home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
iesg
/
iesg.92-05-04
< prev
next >
Wrap
Text File
|
1993-02-04
|
10KB
|
302 lines
IETF STEERING GROUP (IESG)
REPORT FROM THE TELECONFERENCE
May 4th, 1992
Reported by: Greg Vaudreuil, IESG Secretary
This report contains
- Meeting Agenda
- Meeting Attendees
- Meeting Notes
Please contact IESG Secretary Greg Vaudreuil for more information.
ATTENDEES
----------
Almquist, Philip / Consultant
Borman, David / Cray Research
Chiappa, Noel
Crocker, Dave / TBO
Crocker, Steve / TIS
Coya, Steve / CNRI
Davin, Chuck / MIT
Estrada, Susan / CERFnet
Gross, Philip / ANS
Hobby, Russ / UC-Davis
Huizer, Erik / SURFnet
Reynolds, Joyce / ISI
Piscitello, Dave/ Bellcore
Stockman, Bernard / SUNET/NORDUnet
Vaudreuil, Greg / CNRI
Regrets
Hinden, Robert / SUN
AGENDA
-------
1. Administrivia
1.1 Bash the Agenda
1.2 Approval of the Minutes
1.2.1 Minutes of March 26
1.2.2 Minutes of April 2nd
1.2.3 Minutes of April 16th
1.3 Next Meeting
2.0 Protocol Actions
2.1 PPP Authentication
2.2 SNMP Security
2.3 BGP Next Hop SNPA Attribute
3.0 Old Protocol Actions
Proposed Standards
3.1 RFC 1144 Van Jacobsen Header Compression
3.2 RFC 1139 ISO "PING"
3.3 RFC 1094 NFS
3.4 RFC 1057 RPC
3.5 RFC 1056 PCMAIL
3.6 RFC 1037 NFILE
3.7 RFC 1026, 987 X.400(84) <=> RFC 822
3.8 RFC 977 NNTP
3.9 RFC 953 Hostname Server
3.10 RFC 913 SFTP
3.11 RFC 887 Resource Location
3.12 RFC 734 SUPDUP
Draft Standards
3.13 RFC 1084 BOOTP
3.14 RFC 951 Bootstrap Protocol
3.15 RFC 783 TFTP
4.0 Technical Management Issues
4.1 ROAD Recommendation
4.2 Review of Reporting
4.3 Remote Database Access over TCP
4.4 Dead/Sleeping Working Groups
4.5 The Omnipotent IPLPDN
4.6 TSIG Interactions
4.7 IP Address Assignment
5.0 Working Group Actions
To be created
5.1 Network Access Servers (nasreq)
To be reviewed
5.2 Router Discovery
5.3 Bridge MIB
5.4 Decnet Phase IV MIB
MINUTES
-------
1. Administrivia
1.1 Review of the Agenda
The Agenda was review and amended. The IESG decided to pursue the
technical agenda and defer work on the grandfathered protocols until
the next meeting.
1.2 Approval of the Minutes
1.2.1 Minutes of March 26
The Minutes of March 26th were the subject of significant
discussion. A new version has been requested prior to approval.
1.2.2 Minutes of April 2nd
1.2.3 Minutes of April 16th
The Minutes of the April 2nd and 16th Teleconferences were
approved.
1.3 Next Meeting
The IESG agreed to meet next Monday, May 11th to review the
backlogged old protocols.
2.0 Protocol Actions
2.1 PPP Authentication.
There remain a few unresolved issues with this document. The author
has been on vacation and no progress has been made. Final
resolution is expected by the next teleconference.
2.2 SNMP Security.
The Author of the SNMP Security documents and the IAB continue to
work on editorial issues. New documents are expected shortly.
2.3 BGP Next Hop SNPA Attribute.
Bob Hinden was not present to give a report on the BGP working
groups response to IAB questions on this protocol.
3.0 Old Protocol Actions
The IESG deferred discussion on the list of protocol actions until
the next teleconference.
4.0 Technical Management Issues
4.1 ROAD Recommendation
Philip Almquist continues to work on the draft IESG recommendation
on Routing and Addressing. Progress is being made, and a draft
document is expected soon.
4.2 Review of Reporting
The IESG reviewed the new reporting tools of the IETF Secretariat.
To facilitate better dissemination of this information, these reports
will be made available in the distributed IESG directories, updated
weekly.
Action: Vaudreuil -- Send a note to the IESG with the filenames of the
tracking reports in the IESG directory.
The IETF Secretariat was asked about arranging the IETF directory
into a more manageable structure. It was noted that with over 500
files, it was easy to drown in data. The current structure is
dictated by installed shadow directory updating software.
4.3 Remote Database Access over TCP.
The IETF Network Database Working Group has been working on a
standard for running SQL over TCP. An external group, SQLAcess has
been working on the same, and now that their specification is nearly
complete, they would like to submit it to the IETF for
standardization.
The IESG discussed this possible submission. SQLAccess should
publish their specification in the Internet Drafts Directory. The
specification will then be reviewed in the IETF, either by the
Network Database working group, or in another group. This proposal
competes with the Network Database work, and if a harmonization is
not likely, a separate working group can be set up to review the
proposal.
ACTION: Hobby -- Communicate the IETF requirements of open review and
the IAB requirements for change control. Encourage SQLAccess to post their
specification as an Internet Draft and arrange for an IETF review if
requested.
4.4 Dead/Dormant Working Groups
The IAB has suggested that protocols in the standards track have a
"home" in a current working group. The tradition has been for a
working group to disband or become inactive during the period of
implementation and testing between Proposed and Draft Standard.
These groups are recorded by the IESG as "concluded" but their
mailing lists continue as implementors forums.
The IESG discussed the possibility of a new status of Dormant, but
concluded that there is little to be gained. A working group can be
reconstituted by the IESG at any time to re-evaluate a protocol.
There are advantages to "concluding" a working group when the
charter is finished. Concluding a working group has the effect of
closing the door on a "finished" protocol and preventing incremental
featurism.
The IESG agrees with the IAB that there needs to be a "forum" for
discussing a protocol in the standards process, and in fact this
"forum" will be the mailing list of the "concluded" Working Group.
Should the Working Group need to be reformed, this mailing list can
be used as the new Working Group mailing list.
POSITION: The IESG discussed and agreed that Proposed Standard and
Draft Standard RFC's should have the name of the discussion group
listed where questions can be answered and bugs reported in the
protocols.
ACTION: D. Crocker -- Take the discussion on dead and dormant working
groups and prepare a first draft of a position to be communicated to
the IAB.
4.5 IPLPDN
A proposal was made for the IPLPDN working group to begin work on a
CLNP over SMDS standard. This proposed work item raised the
question again about the charter of the IPLPDN group. The issues of
LPDN routing affect both IP and CLNP and the participants of the
working group aim for solutions that are compatible with both
protocols. To further this goal while not seizing the
standardization of ISO protocols, the IESG agreed that work on CLNP
over SMDS can continue as an "experimental" or "Informational"
effort.
4.6 TSIG
Steve Crocker attended the last TSIG meeting and opened a discussion
on mechanisms to work with the IETF. It was a productive meeting in
which TSIG agreed to meet jointly with the IETF at the Boston and
Columbus meetings. Closer coordination in the formation of TSIG and
IETF work items was discussed, and both groups agreed to a closer
working relationship.
A mailing list <ietf-tsig-interactions@tis.com> was set up to
include interested IESG'ers, IETF Secretariat Staff, and TSIG
organizers. Discussions on logistical details and arrangements will
occur on this list. General questions on IETF interactions with
external groups will continue in the context of the Rare working
groups.
4.7 Addressing Assignment Plan for CIDR.
Although we have not yet formed a specific working group to work on
this topic, there are several forums (both inside and outside the
IETF) where discussions are already taking place. Presumably, all
these discussions will contribute to the creation of Internet IP
addressing plan. The IESG asked Bernhard Stackman to act as a point
of coordination for these discussions, in his roles as IESG
Operational Requirements Area Director, in RIPE and in IEPG. Phill
Gross will approach the FEPG and FNC for advice on how to proceed on
the creation of the plan, and then report back to the IESG. After
Bernhard and Phill have talked with these various organizations, the
IESG will decide how to proceed. The goal is to have a firm
foundation for plan going into the boston IETF meeting in July.
5.0 Working Group actions
5.1 Network Access Servers Requirements (nasreq)
The nasreq working group appears to deal primarily with access
control issues, with a sprinkling of service questions. As such,
the IESG agreed to work on chartering this working group in the
Security Area.
ACTION: Steve Crocker -- Review the nasreq charter with the SAAG and
re-submit it to the IESG for consideration of the review.
5.2 Router Discovery
With the clarification of the IESG policy on concluding working
groups, the Router Discovery working group was concluded. The
mailing list will continue as a forum for implementors.
5 .3 Bridge MIB
The Bridge MIB working group will continue to resolve issues of
harmonizing the Bridge MIB with the IEEE Specification.
5.4 Decnet IV
With the clarification of the IESG policy on concluding working
groups, the Decnet Phase IV MIB working group was concluded. The
mailing list will continue as a forum for implementors.
ACTION: Vaudreuil -- Send a draft announcement of the conclusion of the
Router Discovery and Decnet Phase IV MIB working groups to the IESG
list.